bind and short TLD problems?

[nexusis]

I'm new to ispCP - just upgraded a server from a RH5.2 install (where everything was manual and worked fine) and am now running ispCP 1.0.5 on Debian (Debian 4.1.2-25 according to /proc/version)

I have ~12 domains on this particular server, and all run fine except for 2... both are in the .CA TLD. However the registrars for the domains are different. The only commonality I can see is that they are .CA . I think its unlikely that the TLD itself is an issue - but perhaps the length is?

Is there a problem/configuration issue with short TLDs in the default install of ispCP 1.0.5?

The specific problem I'm seeing is that the dns entries will not resolve...

Bind is loading the zone - daemon.log shows the zone reloads and no errors are being thrown

Jul 15 01:55:45 apollo named[19272]: zone domain.ca/IN: loaded serial 2010071000
Jul 15 01:55:45 apollo named[19272]: zone domain.ca/IN: sending notifies (serial 2010071000)

but if I query the local name server I see errors

> server server.com
Default server: server.com
Address: ::ffff:a.b.c.d#53
Default server: server.com
Address: a.b.c.d#53
Default server: server.com
Address: a.b.c.d#53
> domain.ca
Server: server.com
Address: ::ffff:server.com#53

** server can't find domain.ca: NXDOMAIN

but queries for other domains on the host work just fine

> domain2.com
Server: server.com
Address: ::ffff:a.b.c.d#53

Name: domain2.com
Address: g.h.i.j
>

I suppose I could just replace the .db file with the one that I know was working previously (my rh5.2 also ran Bind9) - but I dont want to mess up how ispCP is managing things...

Any insights?

[Nuxwin]

Hello ;

Code:

# ls /var/cache/bind

???

[nexusis]

(07-16-2010 03:48 AM)Nuxwin Wrote:  Hello ;

Code:

# ls /var/cache/bind

???

Forwarded in email due to confidentiality.

the .db file associated with the domain.ca is populated correctly (well, from what I can tell/in comparison to the other .db files).

[Nuxwin]

Ok, I've received. I see two tld CA. What is the content of your /etc/resolv.conf ?

Try to put the following entry in first position in this file:

nameserver 127.0.0.1

After, restart Bind and try again to interrogate (locally) it for these both domains

Maybe the glue record for these both domain point to another server. That can be the reason.

---

Edit:

For the related domain, I've this error:

Quote:nuxwin@dev:~$ dig domain.ca

; <<>> DiG 9.6-ESV-R1 <<>> domain.ca
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 38997
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;domain.ca. IN A

;; Query time: 505 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Jul 15 20:54:44 2010
;; MSG SIZE rcvd: 34

---

If you want, I can check on your server directly. For that, send me the login information. In my opinion, the zone files are wrong for these both domain names.

---

The current name Servers for the first ca domain (Made in WHOIS) in the mail that I have received are:

Code:

ns.propagation.net
ns2.propagation.net

It's the names of your servers name or not ?

---

Edit, the second CA tld domain name cxxsexxxxxxxxxservices.ca as listed in the mail that I have received works. It point to your ispCP login page (It's another problem...).

Only bxxxxxxs-plus.ca don't work.

[nexusis]

(07-16-2010 04:48 AM)Nuxwin Wrote:  Ok, I've received. I see two tld CA. What is the content of your /etc/resolv.conf ?

Try to put the following entry in first position in this file:

nameserver 127.0.0.1

After, restart Bind and try again to interrogate (locally) it for these both domains

That seems to have fixed things.... local query to server now returns the correct responses. Remote requests also return correct responses.

The site is up and running - now I just need to see mail flowing through to make everyone happy. Test emails are still not showing in the mail.log file... could just be a dns propagation issue...