domains names not resolving

Re: domains names not resolving

From:

Date:

Time:

At 4:29 PM +0800 8/15/01, ferdinand.mangio@webphilippines.com wrote:
>Why can't mbc.com.ph and ics.com.ph be browse from our client side using
>another ISP? Is there a problem with our dns settings
>(dns.webphilippines.com.ph)? It started 5 days ago because of a
>defective switch but now it was replaced.

Let's look at the delegation records.

from f.root-servers.net:
ph. NS auth00.ns.uu.net.
ph. NS auth50.ns.uu.net.
ph. NS makisig.iphil.net.
ph. NS ns.eu.net.
ph. NS ns.ripe.net.
ph. NS ns.uu.net.

from ns.eu.net:
mbc.com.ph. NS ns1.webphilippines.com.ph.
mbc.com.ph. NS ns2.webphilippines.com.ph.

(Note that there is no "com.ph" zone - all x.com.ph zones are
delegated directly from the ph zone. Note also that no glue records
were given with this delegation.)

also from ns.eu.net:
webphilippines.com.ph. NS dns.webphilippines.com.ph.
webphilippines.com.ph. NS mozcom.com.
dns.webphilippines.com.ph. A 208.160.224.129

from dns.webphilippines.com.ph:
ns1.webphilippines.com.ph. A 208.160.224.129
ns2.webphilippines.com.ph. A 208.160.224.129

(I note that this has changed since I first looked at it -
originally, these were CNAME records pointing at
dns.webphilippines.com.ph. Also, note that mozcom.com doesn't respond
to DNS queries.)

from your server:
mbc.com.ph. A 208.160.224.131

So it looks like you've fixed the only really serious problem you
had, which was the CNAME records for ns1 and
ns2.webphilippines.com.ph. Now, you're left with the fact that it
takes up to 5 queries (not counting lame delegations) to find the
record. You can shorten this by:

- Remove any dead servers from the delegation - specifically, remove
mozcom.com.

- Create a second DNS server of your own. Assign it the name
ns2.webphilippines.com.ph.

- Change the delegation records in the ph zone to point your domain
to ns1 and ns2, instead of dns and a dead server. This way, the
addresses of ns1 and ns2 will be stored as glue records in the ph
zone. This will remove a couple of steps from the chain of queries
required to look up the data for mbc.com.ph.
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com We Make DNS Easy!

>Based on what we observed all our domains registered with Network
>Solution was resolved immediately as soon as we replaced the switch.
>But domains ending mostly with .ph still has problems.
>
>We already change refresh, retry, expire, minimum and ttl to 600
>seconds, but for 3 days now the domain ending with .ph is still can't
>be resolved.

Don't change the Expire value to less than 1 week - doing so is a
generally bad idea. (Of course. if you don't have a secondary server,
it's no problem.)

>What values are appropriate if we want domain information to
>propagate immediately. Is it a good idea for our DNS to use forwarders?

For immediate propagation, set your Minimum field to a low value,
such as 300 seconds. Be prepared, however, for an increase in DNS
traffic to your server.

The Refresh, Retry, and Expire value have to do with how often your
secondary server (if any) checks for updates.

Use of forwarders is totally unrelated to the question. It only has
to do with how your server looks up other peoples' domain names.

Sales:
888/4-DPOINT

Support:
858/452-3696