Link to home
Start Free TrialLog in
Avatar of tflai
tflai

asked on

Configure DNS

My company have one internal DNS and one external DNS server in the DMZ.  Recently we were having problem connecting to one of the external websites.  After updating some settings, we are able to connection to the site on our external DNS server.  However, on our internal DNS server, we can only connect to the site if we enter xxxxxx.com without the www.  If we browse using www.xxxxxx.com, then we can't connect to the site.

Using NSLOOKUP, xxxxxx.com returns the correct IP address, and www.xxxxxx.com does not on the internal DNS server.

Any ideas how I can fix the problem?  Thanks.
Avatar of Erik Nettekoven
Erik Nettekoven
Flag of Netherlands image

From the currently description it sounds like the forware lookup zone for xxxxxx.com is missing a host (A) record for www. Is there such a record in the zone? If not please create one. Or else could you elaborate a little more about your DNS installation? Which lookup zones and such?
Avatar of Sajid Shaik M
it seems that xxxxx.com is resolving from local dns and it should have A record in the forward lookup zone...

check the dns forwarders and create them properly to resolve the issue...

all the best
Avatar of tflai
tflai

ASKER

The xxxxxx.com is an external website so it should be forwarded to the external DNS and the to our ISP DNS.  The external DNS works just fine.  But somehow www.xxxxxx.com is not being forward to the external DNS properly.  Any suggestions?
ASKER CERTIFIED SOLUTION
Avatar of Erik Nettekoven
Erik Nettekoven
Flag of Netherlands image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of tflai

ASKER

On the internal DNS server, should I check "Do not use reursion for this domain" under Forwarders tab?
You could try for troubleshooting, but it only will return a failure message earlier.

Do not use recursion for this domain: Specifies that ths DNS server not attept any further recursion if the forwarder fail. If the forewarding fails to resolve a query, a failure message is returned.

Can you try to do a nslookup and then set the server to the ip address of the forwarder and then look if what it returns for www.xxxxxxxx.com ?
Avatar of tflai

ASKER

What is a walkaround for this problem?  Can I add a record for www.xxxxxx.com in the Internal DNS's Forward Lookup Zone to force it to work?  If yes, please show me how it can be done?

Thanks.
you could create a forward lookup zone "www.xxxxxx.com" and then add an empty record to (no dns name) but with the ip address of www.xxxxxxx.com.
or else add a forward lookup zone to the internal dns xxxxx.com and add www (and other external records) as A records pointing to the external ip address.
Avatar of tflai

ASKER

Thanks to everyone's replies.  It turned out that the information at the DNS cache for this particular site were not updated.  So I forced a refresh and the problem was resolved.  Thanks.