IPv6 WWW service

[Mohsen Souissi]

Fahad,

It seems to me the observation below made by Michal Ludvig remains
true even if you have got dozens of "It works for" answers.

You DNS configuration is inconsistent.

To help you fix it, here are some 'dig' command output extracts:

1) Lookup the delegation information at the parent zone

------------------------------------------------------------------------
; <<>> DiG 9.6.1-P1 <<>> @a.gtld-servers.net xpedientonline.net ns +norec
[...]
;; flags: qr; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
[...]
;; ANSWER SECTION:
xpedientonline.net.	172800	IN	NS	csns5.cyber.net.pk.
xpedientonline.net.	172800	IN	NS	ns1.cyber.net.pk.
[...]
;; SERVER: 2001:503:a83e::2:30#53(2001:503:a83e::2:30)
------------------------------------------------------------------------

2) Ask each of these two NS's who are the effective authoritative NS's
for the same zone

2.1.
---

------------------------------------------------------------------------
; <<>> DiG 9.6.1-P1 <<>> @ns1.cyber.net.pk xpedientonline.net ns +norec
[...]
;; flags: qr aa; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2

[...]
;; ANSWER SECTION:
xpedientonline.net.	86400	IN	NS	ns.cyber.net.pk.
xpedientonline.net.	86400	IN	NS	ns1.cyber.net.pk.

[...]
;; SERVER: 202.163.96.4#53(202.163.96.4)
------------------------------------------------------------------------

==> Note ns1.cyber.net.pk was not listed in the parent zone (delegation)


A further query to check if ns.cyber... is a serious one.

------------------------------------------------------------------------
; <<>> DiG 9.6.1-P1 <<>> @ns.cyber.net.pk xpedientonline.net ns +norec
[...]
;; flags: qr aa; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2

[...]

;; ANSWER SECTION:
xpedientonline.net.	86400	IN	NS	ns1.cyber.net.pk.
xpedientonline.net.	86400	IN	NS	ns.cyber.net.pk.

[...]

;; SERVER: 202.163.96.3#53(202.163.96.3)
------------------------------------------------------------------------

==> That's the case. There is consitency between information served by both ns
and ns1.

2.2
---

------------------------------------------------------------------------
; <<>> DiG 9.6.1-P1 <<>> @csns5.cyber.net.pk xpedientonline.net ns +norec
[...]
;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
[...]
;; ANSWER SECTION:
xpedientonline.net.	86400	IN	NS	ns.xpedientonline.net.

;; ADDITIONAL SECTION:
ns.xpedientonline.net.	86400	IN	A	61.5.158.121

;; SERVER: 61.5.158.121#53(61.5.158.121)
------------------------------------------------------------------------

==> This is a problem. Not only csns5 does not say the same thing as
the parent zone but it gives a a set of NS's with an empty
intersection with the one given by the parent... This may lead to big
trouble in other situations...


Let's see if the new NS is a serious one:

------------------------------------------------------------------------
dig @ns.xpedientonline.net xpedientonline.net ns
dig: couldn't get address for 'ns.xpedientonline.net': not found
------------------------------------------------------------------------

==> A resolution problem encountered...

Let's see if the IPv4 address provides better results:

------------------------------------------------------------------------
; <<>> DiG 9.6.1-P1 <<>> @61.5.158.121 xpedientonline.net ns +norec
;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

[...]

;; ANSWER SECTION:
xpedientonline.net.	86400	IN	NS	ns.xpedientonline.net.

;; ADDITIONAL SECTION:
ns.xpedientonline.net.	86400	IN	A	61.5.158.121

;; SERVER: 61.5.158.121#53(61.5.158.121)
------------------------------------------------------------------------

==> It seems to claim, I'm authoritative for xpedientonline.net. and
I'm officially the only one... Very different from what the parent
(.net) says


Conclusion, your DNS works almost by chance, thanks to the working DNS
chain provided by ns1. I urge you then to fix your DNS configuration.

Mohsen.

 On 24 Nov, Michal Ludvig wrote:
 | On 11/24/2009 09:15 PM, FAHAD ALI KHAN wrote:
 | > Do DNS get resolve for fahad.xpedientonline.net
 | 
 | Your zone is not consistent. .net resolvers have these NS records for
 | xpedientonline.net:
 | 
 | xpedientonline.net.     172800  IN      NS      csns5.cyber.net.pk.
 | xpedientonline.net.     172800  IN      NS      ns1.cyber.net.pk.
 | 
 | However the zones are completely different on both - csns5 doesn't know
 | anything about fahad.xpedientonline.net. That's why some clients see
 | your blog and some don't.
 | 
 | Fix your NS delegations and you'll see how things suddenly improve ;-)
 | 
 | Michal