All domains work except the newest.

B

Britt

Verified User
Joined
Feb 7, 2007
Messages
16
I have several domains, some under the admin reseller account, and some under user accounts. I tried to set up jaylandings.com as a user account, and it doesnt resolve. The other sites have no issues. I tried setting up a raq2 as ns2.hostingus.com and that didnt help, I moved ns2 back to the main server and it still has the same problem, even though ns2 seems to have other issues now.

I checked the registrar records and the NSs are identical to the other domains on the server. I checked the zone and named files and everything looks right. I need an idea of where to start again since I have spent a few days trying to get it fixed and I am not even sure if I tried things 3-4 times and may have skipped something out of frustration.

The server is Centos 5.5 and the domains shown below are all on the same server but only one has issues. I had problems before trying to set up a domain, DA seemed to not want to insert the correct info, but that was corrected (I think).

Admin reseller account http://www.intodns.com/betterdiver.com
User account site http://www.intodns.com/alpha-marketing.com
Previous Problem Account http://www.intodns.com/titlescuba.com
Current Problem Account http://www.intodns.com/jaylandings.com

Any info, help, ideas, or a pound of explosives would be appreciated.
 
NS2 doesnt reply at all.
Your SOA record is wrong, i would suggest to remove the dns for that domain and re-add it again.

And wait up to 48hrs for dns propagation.

Regards
 
Dropped the domain, removed all references to it on the server, waited a few days (made easy by the weather in this area, tornado's solved the power problem for about 4 days) went back in and set it up again and once again, its doing the same thing.

Anyone have any idea why this is happening?

http://www.intodns.com/jaylandings.com
 
What are you using to replicate dns zone to secondary nameserver? Are nameserver correct? Have you firewall blocking named port?
 
SeLLeRoNe said:
What are you using to replicate dns zone to secondary nameserver? Are nameserver correct? Have you firewall blocking named port?
Click to expand...

I had the secondary DNS on a RAQ2 that I had as an extra but I moved the secondary DNS back on to the DA server since it was working with the other domains on the same server before. It shows as a nameserver in DA but thats the extent of it.

The nameservers are correct in the registration and at the registrar site.

I checked for a firewall on the cable modem before and there is none. I was thinking about putting one on after this problem gets fixed, but it may be easier to just leave it open, it doesnt seem to work anyway. ;)

The secondary doesnt show up in the ifconfig, but in DA, it is there.

DA Screen:

70.88.27.217 server 8 ns1.hostingus.com 255.255.255.0
70.88.27.218 server 0 ns2.hostingus.com 255.255.255.0
70.88.27.219 free admin 255.255.255.0
70.88.27.220 free admin 255.255.255.0

My ifconfig is:
eth0 Link encap:Ethernet HWaddr 00:1A:70:11:46:C0
inet addr:70.88.27.217 Bcast:70.88.27.255 Mask:255.255.255.0
inet6 addr: fe80::21a:70ff:fe11:46c0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:577086 errors:0 dropped:0 overruns:0 frame:0
TX packets:446648 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:77068935 (73.4 MiB) TX bytes:202230251 (192.8 MiB)
Interrupt:66 Base address:0xa800

eth0:0 Link encap:Ethernet HWaddr 00:1A:70:11:46:C0
inet addr:70.88.27.219 Bcast:70.88.27.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:66 Base address:0xa800

eth0:1 Link encap:Ethernet HWaddr 00:1A:70:11:46:C0
inet addr:70.88.27.220 Bcast:70.88.27.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:66 Base address:0xa800

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:262729 errors:0 dropped:0 overruns:0 frame:0
TX packets:262729 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:18605514 (17.7 MiB) TX bytes:18605514 (17.7 MiB)


I spent several hours getting titlescuba.com up and running, and I have tried the same thing with jaylandings.com to get it working. I am seriously starting to think that moving DA from my FreeBSD 5 server to the Centos 5.5 was a bad idea, things just don't seem to work the same. I went 5 years with FreeBSD with hardly any problems, since i changed, I spend more time fixing little things than I do actually working.
 
I added the 2nd DNS, latest ifconfig:

eth0 Link encap:Ethernet HWaddr 00:1A:70:11:46:C0
inet addr:70.88.27.217 Bcast:70.88.27.255 Mask:255.255.255.0
inet6 addr: fe80::21a:70ff:fe11:46c0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:581856 errors:0 dropped:0 overruns:0 frame:0
TX packets:450075 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:77794361 (74.1 MiB) TX bytes:203228437 (193.8 MiB)
Interrupt:66 Base address:0xa800

eth0:0 Link encap:Ethernet HWaddr 00:1A:70:11:46:C0
inet addr:70.88.27.219 Bcast:70.88.27.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:66 Base address:0xa800

eth0:1 Link encap:Ethernet HWaddr 00:1A:70:11:46:C0
inet addr:70.88.27.220 Bcast:70.88.27.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:66 Base address:0xa800

eth0:2 Link encap:Ethernet HWaddr 00:1A:70:11:46:C0
inet addr:70.88.27.218 Bcast:70.255.255.255 Mask:255.0.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:66 Base address:0xa800

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:264975 errors:0 dropped:0 overruns:0 frame:0
TX packets:264975 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:18734954 (17.8 MiB) TX bytes:18734954 (17.8 MiB)
 
Now the IP is pingable. But DNS service is not working properly:

Code: 
>nslookup jaylandings.com 70.88.27.217
Server:  hostingus.com
Address:  70.88.27.217

*** hostingus.com can't find jaylandings.com: Server failed

>nslookup jaylandings.com 70.88.27.218
DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  70.88.27.218

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to UnKnown timed-out

Make sure bind is running. And post here, please, full zone for jaylandings.com from jaylandings.com.db
 
jaylandings.com.db:

$TTL 14400
@ IN SOA ns1.hostingus.com. hostmaster.jaylandings.com. (
2011050400
14400
3600
1209600
86400 )

jaylandings.com. 14400 IN NS ns1.hostingus.com.
jaylandings.com. 14400 IN NS ns2.hostingus.com.

ftp 14400 IN A 70.88.27.217
jaylandings.com. 14400 IN A 70.88.27.217
localhost 14400 IN A 127.0.0.1
mail 14400 IN A 70.88.27.217
pop 14400 IN A 70.88.27.217
smtp 14400 IN A 70.88.27.217
www 14400 IN A 70.88.27.217

jaylandings.com. 14400 IN MX 10 mail


217.27.88.70.in-addr.arpa. 14400 IN PTR jaylandings.com.

jaylandings.com. 14400 IN TXT "v=spf1 a mx ip4:70.88.27.217 ~$

localhost 14400 IN AAAA ::1

If Bind wasnt running, wouldnt the rest of the domains not show or be able to be routed to? What is the command to check bind on a centos box? I used ./named-checkconf /etc/named.conf with no reply, which should mean there are no errors, correct?

jaylandings.com.conf:

UseCanonicalName=OFF
bandwidth=unlimited
cgi=ON
defaultdomain=yes
domain=jaylandings.com
ip=70.88.27.217
open_basedir=ON
php=ON
quota=unlimited
safemode=OFF
ssl=OFF
suspended=no
username=jayland
 
You might want to delete this record

217.27.88.70.in-addr.arpa. 14400 IN PTR jaylandings.com.
Click to expand...

from zone jaylandings.com. PTR records should be changed at your upstream.

I can't say what exactly is wrong with your server. One thing I know, that something is definitely wrong configured. It can be either firewall or any related software, or your copy of named.

Post here results for:

Code: 
netstat -an | egrep ^"tcp|udp" | grep LISTEN | grep \:53
 
tcp 0 0 70.88.27.217:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
 
Is it now clear how to solve the problem? Make your bind to listen all interfaces, or at least add those IPs, which are supposed to be responsible to answer the DNS request.
 
The same way as on FreeBSD. named.conf is OS independent. The only difference might be its location. Please refer to handbook or manual in order to find details on configuring named.
 
I looked again in intodns .. i had the same a year ago, but there was a missing action what i had to do on the registrar site - i had registered my nameservers with their IPs there, the right entries in the zonefile there, and they looked the same as now here, but it was additional necessary to go under the domainmanagement - also on registrarsite - where I could switch the NS to a domain, and there to simply click in the domainmanagement to apply (even without new values, i did it with the same NS!) - it may depend on the registrarmanagement, in my case i had to do this "update" again, after the ns-registry-entries, and after 24-48h - voila.
Hope its helps.
 
tcp 0 0 70.88.27.218:53 0.0.0.0:* LISTEN
tcp 0 0 70.88.27.217:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN


I added .218 to named.conf, restarted named, waited awhile, and still nothing. I checked the registrars site again, everything is good there. What else could be going wrong? I have been using DA too long to switch, there has to be a way to fix this and I cant keep putting off the owner of the domain forever.
 
Sorry to say, but that's becoming a little bit bothersome, your named responds partly. What has your registrar to do with that? None progress is done:

Code: 
# nslookup jaylandings.com 70.88.27.217
Server:         70.88.27.217
Address:        70.88.27.217#53

** server can't find jaylandings.com: SERVFAIL

# nslookup jaylandings.com 70.88.27.218
Server:         70.88.27.218
Address:        70.88.27.218#53

** server can't find jaylandings.com: SERVFAIL

Can you do simple testing with nslookup or dig? I do not know how wrong is configured your named.conf (I'm not any kind of fortuneteller), but it seems it should be re-configured. I can try and do that within one hour with root access to your server, but this will cost you some dollars.

Post your full named.conf

p.s. At least no reds for http://www.intodns.com/betterdiver.com
 
// generated by named-bootconf.pl

options {
listen-on port 53 { 127.0.0.1; 70.88.27.217; 70.88.27.218; };
directory "/var/named";
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
query-source address * port 53;

allow-transfer { none; };
allow-recursion { localnets; };
};

//
// a caching only nameserver config
//
controls {
inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
zone "." IN {
type hint;
file "named.ca";
};

zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};

zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};

include "/etc/rndc.key";

zone "217.27.88.70.in-addr.arpa" { type master; file "/var/named/217.27.88.70.in-addr.arpa.db"; };
zone "hostingus.com" { type master; file "/var/named/hostingus.com.db"; };
zone "alpha-marketing.com" { type master; file "/var/named/alpha-marketing.com.db"; };
zone "hostingus.net" { type master; file "/var/named/hostingus.net.db"; };
zone "bentaxe.com" { type master; file "/var/named/bentaxe.com.db"; };
zone "betterdiver.com" { type master; file "/var/named/betterdiver.com.db"; };
zone "betterdiver.net" { type master; file "/var/named/betterdiver.net.db"; };
zone "titlescuba.com" { type master; file "/var/named/titlescuba.com.db"; };
zone "jaylandings.com" { type master; file "/var/named/jaylandings.com.db"; };
 
You must log in or register to reply here.
Back
Top