Operation of DNS server

In message <iatkbe$l8i$(E-Mail Removed)>, sl@exabyte wrote:

> When I do a 'nslookup/dig' in the morning, very frequently it reports the
> domain cannot be reached.
>
> When I specify another DNS server, eg google's 8.8.4.4, it returns the IP
> of the server.
>
> In the afternoon when I do the DNS query again using my ISP's DNS server,
> it returns the correct IP.
>
> This scenario repeats the next day.

Maybe they’re doing zone transfers over short wave ...

sl@exabyte <(E-Mail Removed)> wrote:
> There is a domain that my ISP's DNS server seems to have a problem.
> Is there something wrong with my ISP's DNS server ?

There might be. Have you checked whether you have the same problem for
a different domain on your ISP's DNS server? On the basis that your ISP
isn't a two-bit cowboy outfit, what about trying its other DNS server(s)?

What about telling us the query you're trying, and the time(s) you're
trying it, so that someone "out here" can attempt to replicate your
issue. (On the other hand, if your ISP uses anycast DNS then the results
won't be predictable anyway.)

Have you reported this issue to your ISP?
Chris

There is a domain that my ISP's DNS server seems to have a problem.

When I do a 'nslookup/dig' in the morning, very frequently it reports the
domain cannot be reached.

When I specify another DNS server, eg google's 8.8.4.4, it returns the IP of
the server.

In the afternoon when I do the DNS query again using my ISP's DNS server, it
returns the correct IP.

This scenario repeats the next day.

Question
======

Is there something wrong with my ISP's DNS server ?

> There might be. Have you checked whether you have the same problem for
> a different domain on your ISP's DNS server? On the basis that your
> ISP isn't a two-bit cowboy outfit, what about trying its other DNS
> server(s)?
>
> What about telling us the query you're trying, and the time(s) you're
> trying it, so that someone "out here" can attempt to replicate your
> issue. (On the other hand, if your ISP uses anycast DNS then the
> results won't be predictable anyway.)
>
> Have you reported this issue to your ISP?
> Chris

I tried: nslookup sripelangi.com (default DNS server 203.121.65.39)

I never try the 2nd: 203.121.65.30

But I tried another ISP's DNS server: 202.188.0.132

Time: 1000 to 1200

Have not reported to my ISP.

Chris Davies wrote:
>> What about telling us the query you're trying, and the time(s) you're
>> trying it, so that someone "out here" can attempt to replicate your
>> issue.

SL <(E-Mail Removed)> wrote:
> I tried: nslookup sripelangi.com (default DNS server 203.121.65.39)
> I never try the 2nd: 203.121.65.30

What results do you expect? sripelangi.com has nameservers
ns1.my-rialto.com and ns2.my-rialto.com, but neither of these has A
records, so the nameservice for sripelangi.com will fail. It looks like
my-rialto.com is zoned from mschosting.com, so you probably need to
rethink what you're really trying to do.


> But I tried another ISP's DNS server: 202.188.0.132
> Time: 1000 to 1200

Does this mean you got the result you expected, or not?


> Have not reported to my ISP.

Shrug.

Chris

>> I tried: nslookup sripelangi.com (default DNS server 203.121.65.39)
>> I never try the 2nd: 203.121.65.30
>
> What results do you expect? sripelangi.com has nameservers
> ns1.my-rialto.com and ns2.my-rialto.com, but neither of these has A
> records, so the nameservice for sripelangi.com will fail. It looks
> like my-rialto.com is zoned from mschosting.com, so you probably need
> to rethink what you're really trying to do.
>

'ns1.my-rialto.com' and 'ns2.my-rialto.com' don't really exist, I think. The
domain "sripelangi.com" is hosted under a reseller scheme, where the
reseller control panel is under "my-rialto.com".

The ISP DNS serrvers are: ns101.mschosting.com, ns102.mschosting.com

There are times when I am browsing some pages on my ISP servers when
suddenly, the browser cannot locate the server. When I then do a ping, I can
'the domain cannot be reached", and thus "nslookup" will fail.

When I am doing DNS query on broadband, the query will be sent to the
broadband service's DNS server: 203.121.65.39.

Yesterday I did try 203.121.65.30, it succeeded, but 203.121.65.39 fails.

Virus ??


>> But I tried another ISP's DNS server: 202.188.0.132
>> Time: 1000 to 1200
>
> Does this mean you got the result you expected, or not?
>
>
>> Have not reported to my ISP.
>

SL <(E-Mail Removed)> wrote:
> 'ns1.my-rialto.com' and 'ns2.my-rialto.com' don't really exist, I think.

Then you can't have them as nameservers for your domain. Period.
Chris

On Fri, 05 Nov 2010 02:44:16 -0400, SL <(E-Mail Removed)> wrote:

> I tried: nslookup sripelangi.com (default DNS server 203.121.65.39)

The dns entries for sripelangi.com are messed up. The first time
a name server does a lookup, it will use the glue records in the
root servers, to find it.

$ whois sripelangi.com|grep "Name Server"
Name Server: NS101.MSCHOSTING.COM
Name Server: NS102.MSCHOSTING.COM

$ dig -4 +trace sripelangi.com any
<snip>
sripelangi.com. 172800 IN NS ns101.mschosting.com.
sripelangi.com. 172800 IN NS ns102.mschosting.com.
;; Received 115 bytes from 192.52.178.30#53(k.gtld-servers.net) in 137 ms

sripelangi.com. 14400 IN MX 0 sripelangi.com.
sripelangi.com. 86400 IN SOA ns1.my-rialto.com.
ssleng.ec-partners.com. 2010031900 86400 7200 3600000 86400
sripelangi.com. 86400 IN NS ns1.my-rialto.com.
sripelangi.com. 86400 IN NS ns2.my-rialto.com.
sripelangi.com. 14400 IN A 110.4.45.111

The primary master server (ns1.my-rialto.com), does not exist,
so when the A record expires after 14400 seconds (4 hours),
the attempt to refresh the A record from ns1.my-rialto.com will
fail. It will continue to fail until the SOA record gets purged
from that name servers cache, which will happen after 86400 seconds
(24 hours).

I would expect the site to only be accessible, for 4 hours per day,
given the above errors, unless you change name servers. Whoever
maintains the dns for sripelangi.com should fix the name server in
the SOA record.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

>
>> I tried: nslookup sripelangi.com (default DNS server 203.121.65.39)
>
> The dns entries for sripelangi.com are messed up. The first time
> a name server does a lookup, it will use the glue records in the
> root servers, to find it.
>
> $ whois sripelangi.com|grep "Name Server"
> Name Server: NS101.MSCHOSTING.COM
> Name Server: NS102.MSCHOSTING.COM
>
> $ dig -4 +trace sripelangi.com any
> <snip>
> sripelangi.com. 172800 IN NS ns101.mschosting.com.
> sripelangi.com. 172800 IN NS ns102.mschosting.com.
> ;; Received 115 bytes from 192.52.178.30#53(k.gtld-servers.net) in
> 137 ms
> sripelangi.com. 14400 IN MX 0 sripelangi.com.
> sripelangi.com. 86400 IN SOA ns1.my-rialto.com.
> ssleng.ec-partners.com. 2010031900 86400 7200 3600000 86400
> sripelangi.com. 86400 IN NS ns1.my-rialto.com.
> sripelangi.com. 86400 IN NS ns2.my-rialto.com.
> sripelangi.com. 14400 IN A 110.4.45.111
>
> The primary master server (ns1.my-rialto.com), does not exist,
> so when the A record expires after 14400 seconds (4 hours),
> the attempt to refresh the A record from ns1.my-rialto.com will
> fail. It will continue to fail until the SOA record gets purged
> from that name servers cache, which will happen after 86400 seconds
> (24 hours).
>
> I would expect the site to only be accessible, for 4 hours per day,
> given the above errors, unless you change name servers. Whoever
> maintains the dns for sripelangi.com should fix the name server in
> the SOA record.
>
> Regards, Dave Hodgins

Thanks for the info Dave; I have something to dig about now.