K
Kevin D. Goodknecht [MVP]
In
goes and asks you DNS server to resolve the name, it answers with a private
address.
Since you are using your server as authoritative for webajm.com all I needed
to do was ask your nameserver to resolve the name. Which is what any DNS
server will do.
and I can leave my AD naming convention alone or does it
domain. Your AD domain must resolve to private addresses or your internal
domain will break
If you are using the host name of your AD DNS server as an NS in any domain
that needs to be resolved publicly you are going to have very inconsistant
behavior.
Use a different host name for your public NS record, one that only resolves
to a public address from the public side of your router.
It is getting this IP address from the parent gTLD .com servers. But when itAdam Marx said:Kevin, hello again we've spoken before.
I am extremely eager to clear this up.
2 things,
1. You are correct about webajm.com I believe and now know that it is
setup incorrectly. When I run a test from DNSreport.com it points
w2k.ajm1.webajm.com to a public IP? why? I mean isn't that correct?
How did you get a private IP? The server is behind a router and is
essentially using a private IP.
goes and asks you DNS server to resolve the name, it answers with a private
address.
Since you are using your server as authoritative for webajm.com all I needed
to do was ask your nameserver to resolve the name. Which is what any DNS
server will do.
Yes, exactly.If I add a record called NS1 in the zone Webajm.com and point it a
public IP will I then need to register it as NS1.webajm.com with my
registrar?
and I can leave my AD naming convention alone or does it
Do not mix your AD domain or any host in your AD domain in with you publicalso need to be changed? can you walk me through the resolution of
the site webajm.com if someone were looking for it?
domain. Your AD domain must resolve to private addresses or your internal
domain will break
2. I'm actually trying to set up a new domain (correctly)
hostingky.com which is where I am having my problem that is almost
resolved. I am going to assume that it also is setup incorrectly from
you post.
If you are using the host name of your AD DNS server as an NS in any domain
that needs to be resolved publicly you are going to have very inconsistant
behavior.
Use a different host name for your public NS record, one that only resolves
to a public address from the public side of your router.