Manual DNS Entries

  • Thread starter Thread starter jwkh
  • Start date Start date
J

jwkh

I've a DNS server that cannot resolve a FQDN for some
strange reason. The clients on the LAN need to have the
address resolved. I'd like to get around this problem.

I tried adding it to the DNS server's hosts file but it
only resolves for the DNS server.

Is there a manual way to add to the DNS cache on the DNS
server so the LAN clients can resolve it? Maybe a Q
article on it?

TIA,

jwkh
 
In jwkh <[email protected]>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.
I've a DNS server that cannot resolve a FQDN for some
strange reason. The clients on the LAN need to have the
address resolved. I'd like to get around this problem.

I tried adding it to the DNS server's hosts file but it
only resolves for the DNS server.

Is there a manual way to add to the DNS cache on the DNS
server so the LAN clients can resolve it? Maybe a Q
article on it?

TIA,

jwkh
Click to expand...

Are you refering to it cannot resolve internet names or local names?

300202 - HOW TO Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202&FR=1
 
I've got that Q already. Will check the "Root Hints" part.

Basically, I need to add an entry to DNS that will be
available to all LAN clients.

Thanks,

jwkh
 
In jwkh <[email protected]>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.
I've got that Q already. Will check the "Root Hints" part.

Basically, I need to add an entry to DNS that will be
available to all LAN clients.

Thanks,

jwkh
Click to expand...

What host names are you having trouble with?
Is it supposed to be in your domain name?
host files tend slow things up quite a bit.
 
The site has two service providers:

One does the actual Internet connection - DSL.

The other hosts their Web site and email.

There are different DNS for both. If they do not include
the email host DNS in the clients' IP setups, they cannot
resolve the mail site for the email clients.

They have a W2K DC server with AD and DHCP and DNS. The
DNS has forwarders pointing to the DSL DNS sites AND the
email DNS site (DSL is primary and email is secondary).
It STILL does not resolve their email address. Adding to
the DNS server's hosts file does not help.

Still, my point is can I add it manually?

TIA,

jwkh
 
In
jwkh said:
The site has two service providers:

One does the actual Internet connection - DSL.

The other hosts their Web site and email.

There are different DNS for both. If they do not include
the email host DNS in the clients' IP setups, they cannot
resolve the mail site for the email clients.

They have a W2K DC server with AD and DHCP and DNS. The
DNS has forwarders pointing to the DSL DNS sites AND the
email DNS site (DSL is primary and email is secondary).
It STILL does not resolve their email address. Adding to
the DNS server's hosts file does not help.

Still, my point is can I add it manually?

TIA,

jwkh
Click to expand...

You could add it manually. Your description is a bit tough to follow, but
from what I see, I'm assuming that no DNS servers on the Internet can
resolve the mail record, is that correct?

Would be really easier if you provided the actual domain name so we can see
if we can resolve it which would help diagsnoe why your different machines
can't resolve it. But that leads me to something else about using multiple
entries, which is highly NOT advised unless both entries have the SAME exact
zone information. Read on...

Little factoid:
If you have more than one DNS lisd in your IP properties, it won't help, but
may confuse the issue. This is due to multiple listings are meant to be a
fault tolerant solution and NOT a load balancing or for mutliple record
access from both listings. This is because the Windows DNS Client Resolver
service will ask the first one. If it ain't got the answer, or doesn't
respond (server maybe down?), it will then query the second one. But it will
NOT go back to the first one at all, unless of course you either restart the
machine OR you restart the DNS Client Service on the machine.

A good way to get the best of both is use your internal one only, and setup
a forwarder to the ISP's DNS. Not knowing if you have AD or not, this is the
"best practice" that many follow and is the consensus in these newsgroups,
especially when using AD, since AD's reliance on DNS is it's lifeline.
How to create a forwarder you ask?
http://support.microsoft.com/?id=300202
If the option is grayed out, delete your Root zone, also shown in that
article.

So, that said, when you list the two, it will confuse and dilute and give
false results. You would need to try using one, then the other and see which
one will resolve it. You can also use nslookup to resolve it.

Example, using the infamous "domain.com" below:
===================================
C:\>nslookup
Default Server: ponyexpress.bandwidthpros.com
Address: 208.47.39.10

(This is my server above)
(Then I changed it to use 4.2.2.2 below)
server 4.2.2.2
Click to expand...
Default Server: vnsc-bak.sys.gtei.net
Address: 4.2.2.2
set type=mx
domain.com
Click to expand...
Server: vnsc-bak.sys.gtei.net
Address: 4.2.2.2

DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
domain.com MX preference = 10, mail exchanger = mail.domain.com

domain.com nameserver = dns2.domainbank.net
domain.com nameserver = dns1.domainbank.net
mail.domain.com internet address = 127.0.0.1
dns1.domainbank.net internet address = 209.92.33.130
dns2.domainbank.net internet address = 209.92.33.150
(Then I changed it back to use my server again below):
server 208.47.39.10
Click to expand...
Default Server: mail.vbjproductions.com
Address: 208.47.39.10
domain.com
Click to expand...
Server: mail.vbjproductions.com
Address: 208.47.39.10

domain.com MX preference = 10, mail exchanger = mail.domain.com
domain.com nameserver = dns1.domainbank.net
domain.com nameserver = dns2.domainbank.net
mail.domain.com internet address = 127.0.0.1
dns1.domainbank.net internet address = 209.92.33.130
dns2.domainbank.net internet address = 209.92.33.150
exit
Click to expand...
===================================


So, yes, you can create a copy of this zone on YOUR DNS server on your own
LAN that you now have ALL your machines soley using and setup a forwarder
on. Then under that zone, create a mail record for that mail server and give
it the actual external IP address. If you don't know the address, use the
nslookup method I showed above and it will give you the actual external IP.

--
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
 
In jwkh <[email protected]>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.
The site has two service providers:

One does the actual Internet connection - DSL.

The other hosts their Web site and email.

There are different DNS for both. If they do not include
the email host DNS in the clients' IP setups, they cannot
resolve the mail site for the email clients.

They have a W2K DC server with AD and DHCP and DNS. The
DNS has forwarders pointing to the DSL DNS sites AND the
email DNS site (DSL is primary and email is secondary).
It STILL does not resolve their email address. Adding to
the DNS server's hosts file does not help.

Still, my point is can I add it manually?

TIA,

jwkh
Click to expand...



Not sure what you are wanting to add manually. So you have three DNS servers
on site?
For this to work correctly all DNS servers must be able to resolve any name,
you can't have one DNS with domain1 another DNS server with domain2 and
another DNS server with domain3 and then put one DNS in as primary and the
other in as secondary. Any one of these DNS servers must be able to resolve
all names.
The solution put a secondary zone of domain2 and domain3 on the server with
domain1
The same with the othe DNS server the DNS with domain2 should have a
secondary zone for domain1 and domain3 and DNS for domain3 should have a
secondary zone for domain1 and domain2.

This will work and this way all DNS server can resolve all names.
 
Back
Top