Operation of DNS server

Operation of DNS server

Post by s » Sat, 06 Nov 2010 06:56:48



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 ?

 
 
 

Operation of DNS server

Post by habibielwa7i » Fri, 05 Nov 2010 17:22:05



Quote:> 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 ?

May be, But why bother your self with your ISP DNS, Use any others if
more stable, I usually use more than 1 open DNS servers, Sometimes the
ISPs DNS servers are not good, Also you may report the problem to your
ISP so they can check what's wrong with there DNS servers.

 
 
 

Operation of DNS server

Post by Lawrence D'Oliveir » Fri, 05 Nov 2010 17:46:49



Quote:> 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 theyre doing zone transfers over short wave ...
 
 
 

Operation of DNS server

Post by s » Fri, 05 Nov 2010 22:31:29


Quote:> Maybe they're doing zone transfers over short wave ...

New to me; I shall google to find out the meaning :-)

Thanks.

 
 
 

Operation of DNS server

Post by Chris Davie » Sat, 06 Nov 2010 00:33:26



> 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

 
 
 

Operation of DNS server

Post by SL » Sat, 06 Nov 2010 15:44:16


Quote:> 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.

 
 
 

Operation of DNS server

Post by Chris Davie » Sat, 06 Nov 2010 19:09:24



>> 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.

> 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.

Quote:> 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?

Quote:> Have not reported to my ISP.

Shrug.

Chris

 
 
 

Operation of DNS server

Post by David Schwart » Sat, 06 Nov 2010 21:51:30



Quote:> 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.

The zone 'sripelangi.com' is broken. Some perfectly-valid methods of
querying it will work and some equally valid methods will fail.

The nameservers recorded in the registry are not listed as
authoritative in the zone. The two nameservers in the zone do not
exist. Basically, that domain is just a mess.

DS

 
 
 

Operation of DNS server

Post by SL » Sat, 06 Nov 2010 23:29:34


Quote:>> 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 ??

Quote:>> 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.

 
 
 

Operation of DNS server

Post by Chris Davie » Sun, 07 Nov 2010 02:55:08



> '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
 
 
 

Operation of DNS server

Post by David W. Hodgin » Sun, 07 Nov 2010 06:01:44



> 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.)

 
 
 

Operation of DNS server

Post by David Schwart » Sun, 07 Nov 2010 08:27:51



Quote:> 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 ??

As has been explained at least twice, the domain is hopelessly broken.
It's not a virus. It's not a problem with ISP's DNS servers. The
domain is broken. Until it is fixed, it will remain broken.

DS

 
 
 

Operation of DNS server

Post by SL » Sun, 07 Nov 2010 16:24:36


Quote:

>> 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.
 
 
 

1. if DNS server was Windows based what DNS server software is avail?

WSM> And what is "Unices" ;)

JdeBP> I assume that the emoticon indicates disingenuousness on your part.
JdeBP> After all, a 10 second search of the World Wide Web with one's favourite
JdeBP> search engine will turn up a definition of [the] word, and anyone as
JdeBP> proficient with English as yourself and who deals with computers will
JdeBP> have undoubtedly long since encountered the plurals of words such as
JdeBP> "index" and "matrix".

KDGS> Maybe your understanding of the English language is the problem, [...]
KDGS> The plural for Unix is still Unix.

Take the 10 seconds and perform the search.  You'll find plenty of
people telling you what the accepted plural is, and that that isn't
it.  Or read the "comp.unix.questions" FAQ document.

2. yamm information

3. NT dns server request to my LINUX dns server time out

4. Iomega Ditto 3200 Configuration

5. using DNS server(named) and external dns server.

6. What is libXm.so.2 ?

7. dns operations taking very long

8. ne2000 problem

9. remove mixture of non-atomic operations with page->flags which requires atomic operations to access

10. DNS: can I set my dns to forward a web address to another server ?

11. Dynamic DNS not working with Solaris DHCP/DNS server and win clients

12. DNS Problem. WIN98 does not find DNS Server...

13. Dynamic DNS not working with Solaris DHCP/DNS server and win clients