J
Jamal Mubarik
I am confuses. Should the first DNS adress (10.0.0.1) be of the server
itself.
Thank you
itself.
Thank you
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
H
Herb Martin
Your question is somewhat incomplete but presuming we can figure out
the context...
Generally a DNS server should set it's OWN CLIENT properties to point
to itself since presumably it "knows the right answers" and avoiding the
network request is a good thing when all else is equal.
Not only should it be first, it should perhaps be the ONLY entry but if
you add more than one, the others should be "from the same set" -- don't
mix internal servers and external servers on the same CLIENT settings.
Now there are occasionally reasons for breaking this (loose) 'rule' above.
One is where you have a problem with AD DNS replication and you
(perhaps temporarily) point DNS1 -> DNS2 so that it can both register
its AD records and resolve the other server there.
I have a "firewall" which runs a "caching only DNS" but the firewall client
properties are set to an INTERNAL DNS which can resolve the internal
names and then that internal DNS forwards to the "firewall DNS" as it's
forwarder for Internet lookup.
[Note: All internal clients are set to the INTERNAL DNS, so all internal
names resolve but then they forward to the "firewall" which takes care of
ALL EXTERNAL resolution -- but the clients never know this. Even the
"firewall" itself -- as a client -- doesn't know this.]
the context...
Jamal Mubarik said:I am confuses. Should the first DNS adress (10.0.0.1) be of the server
itself.
Generally a DNS server should set it's OWN CLIENT properties to point
to itself since presumably it "knows the right answers" and avoiding the
network request is a good thing when all else is equal.
Not only should it be first, it should perhaps be the ONLY entry but if
you add more than one, the others should be "from the same set" -- don't
mix internal servers and external servers on the same CLIENT settings.
Now there are occasionally reasons for breaking this (loose) 'rule' above.
One is where you have a problem with AD DNS replication and you
(perhaps temporarily) point DNS1 -> DNS2 so that it can both register
its AD records and resolve the other server there.
I have a "firewall" which runs a "caching only DNS" but the firewall client
properties are set to an INTERNAL DNS which can resolve the internal
names and then that internal DNS forwards to the "firewall DNS" as it's
forwarder for Internet lookup.
[Note: All internal clients are set to the INTERNAL DNS, so all internal
names resolve but then they forward to the "firewall" which takes care of
ALL EXTERNAL resolution -- but the clients never know this. Even the
"firewall" itself -- as a client -- doesn't know this.]
A
Ace Fekay [MVP]
In
Follow what Herb suggests. Only use your internal DNS and no other ones or
numerous errors will occur. Use a forwarder for Internet resolution. If the
Forwarding option is grayed out, delete the Root zone.
Read this for more info:
http://support.microsoft.com/?id=291382
How to create a forwarder and delete the root zone:
http://support.microsoft.com/?id=300202
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
Jamal Mubarik said:I am confuses. Should the first DNS adress (10.0.0.1) be of the server
itself.
Thank you
Follow what Herb suggests. Only use your internal DNS and no other ones or
numerous errors will occur. Use a forwarder for Internet resolution. If the
Forwarding option is grayed out, delete the Root zone.
Read this for more info:
http://support.microsoft.com/?id=291382
How to create a forwarder and delete the root zone:
http://support.microsoft.com/?id=300202
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory