merged: DNS & www

[OffPriceC]

Hi,

I have DNS problem I talked with support and they told me to contact my provider Bellsouth, but they told me to replace my current nameservers ns.jaguarpc.net and ns2.jaguarpc.net with theirs I'm not sure if that will be wise, or if it's better to add them and changing the jaguar's NS to positions 3 and 4 ?


thank you

[jason]

You should use the Jaguar servers. That way, if anything changes in your DNS Zone (such as they change your IP address or something), the changes can take effect immeadiatly (from the server end, propagation issues will still occur). Otherwise you will have to wait until you are notified of the change by support so you can notify Bellsouth of the change, then you'll have to wait for them to change it. You could end up seeing some significant downtime that way. Also, listing both JPC and BS (gee, I like that abbr.) is asking for trouble. Since Bellsouth isn't actually doing anything regarding to your site, they shouldn't be listed in your domain record. That's all JPC territory.

--Jason

[jason]

After rereading your post, I think that Bellsouth is telling you to replace the nameservers in your Windows TCP/IP settings with their servers, not the ones for your domain. Generally, though, these days you don't need to set up DNS servers in Windows as your ISP's DHCP server usually tells your system what to use when your first connect. I'm not sure, but I think there is a miscommunication going on here somewhere...

--Jason

[Vin DSL]

Originally posted by jason
After rereading your post, I think that Bellsouth is telling you to replace the nameservers in your Windows TCP/IP settings with their servers, not the ones for your domain...

Damn! I thought I had you that time...

[jason]

Originally posted by Vin DSL
Damn! I thought I had you that time...

I'm just too good...

--Jason

[Vin DSL]

Ever since we were moved to the 'new' server, I've noticed that occasionally my site cannot be reached using:

www.lenon.com (DNS error)

But, it's always reachable using:

lenon.com

What's that all about?

I shelled in and did an 'uptime' on the server. It's reporting 14 days, so that's not the problem.

Maybe a problem with my ISP?!?!?!?

[Vin DSL]

.

[OffPriceC]

Ok but my domain is still having problems and in Jaguar support they told me to contact Bellsouth because they were replicating my domain to my network, we have a DSL router, and what it's happening is the domain is not resolving at all, or it intermitently
resolves and then it stops and so on ...

[JPC-Les]

Could be an ISP issue. "www." resolves from my end.

[lookout]

If you have an .htaccess file, try renaming it to disable it temporarily. Test to see if the problem still occurs after doing so.

[lookout]

I think I see at least one of the problems here. Maybe it's the only one.

Open up a ticket and ask JaguarPC to verify their MX record for your account. It looks like there's a typo of ".con" instead of ".com" there.

A "whois" query on the "offpricecloseouts.com" domain shows you that you have assigned your nameserver pair to ns.jaguarpc.net and ns2.jaguarpc.net. Many of us use one of Jaguar's alternate nameserver pairs. But Jaguar also supports the pair you are currently using, so you should be fine.

The typo reveals itself when one performs a "dig" query on the "offpricecloseouts.com" domain, based off NS.JAGUARPC.NET. The results list nameservers of ns.nocdirect.con and ns2.nocdirect.con. Those should be ns.nocdirect.com and ns2.nocdirect.com.

[Vin DSL]

Originally posted by Les
Could be an ISP issue. "www." resolves from my end.

I agree! It passes the good ol' PROXY test, e.g. works indirectly through a proxy server, but not directly through my ISP. So, the ISP has to be the problem. Must be the zone file that changes. Makes me wonder where they get their info.

Do you think, if I add additional DNS servers to my domain name it will help? That's what I did with previous hosts --- you know, NS, NS1, NS2, NS3, NS4 and so on...

Does JagPC only have 2 domain servers?

[JPC-Greg]

We have ns thru ns6 , plus a few others. Check the network page of the clients section for the dns name servers we run.

[lookout]

Could there be something awry with one the Jaguar nameserver configuration pairs? I noticed Vin is currently using the same NS.JAGUARPC.NET and NS2.JAGUARPC.NET nameservers for his site as the person mentioned in this recent post. A "dig" using NS.JAGUARPC.NET shows the same ".con" nameserver typo on both domains.

Appended:
If this is any help, here's the results of the dig that I am currently seeing. Note the second and third lines:

04/21/03 19:00:40 dig lenon.com @ ns.jaguarpc.net
Dig lenon.com@ns.nocdirect.con failed, no such host
Dig lenon.com@ns2.nocdirect.con failed, no such host
Dig lenon.com@ns.jaguarpc.net (66.227.56.27) ...
Authoritative Answer
Recursive queries supported by this server
Query for lenon.com type=255 class=1
lenon.com MX (Mail Exchanger) Priority: 0 lenon.com
lenon.com SOA (Zone of Authority)
Primary NS: ns.nocdirect.con
Responsible person: admin@nocdirect.com
serial:2003042102
refresh:28800s (8 hours)
retry:7200s (2 hours)
expire:3600000s (410 days)
minimum-ttl:86400s (24 hours)
lenon.com NS (Nameserver) ns.nocdirect.con
lenon.com NS (Nameserver) ns2.nocdirect.con
lenon.com A (Address) 66.227.17.133
lenon.com A (Address) 66.227.17.133

[Vin DSL]

Originally posted by lookout
Could there be something awry with one the Jaguar nameserver configuration pairs?... A "dig" using NS.JAGUARPC.NET shows the same ".con" nameserver typo on both domains.

Appended:
If this is any help, here's the results of the dig that I am currently seeing. Note the second and third lines:

04/21/03 19:00:40 dig lenon.com @ ns.jaguarpc.net
Dig lenon.com@ns.nocdirect.con failed, no such host
Dig lenon.com@ns2.nocdirect.con failed, no such host
Dig lenon.com@ns.jaguarpc.net (66.227.56.27) ...
Authoritative Answer
Recursive queries supported by this server
Query for lenon.com type=255 class=1
lenon.com MX (Mail Exchanger) Priority: 0 lenon.com
lenon.com SOA (Zone of Authority)
Primary NS: ns.nocdirect.con
Responsible person: admin@nocdirect.com
serial:2003042102
refresh:28800s (8 hours)
retry:7200s (2 hours)
expire:3600000s (410 days)
minimum-ttl:86400s (24 hours)
lenon.com NS (Nameserver) ns.nocdirect.con
lenon.com NS (Nameserver) ns2.nocdirect.con
lenon.com A (Address) 66.227.17.133
lenon.com A (Address) 66.227.17.133

I've been messing with a new 'FTP' style proggie most of the day. It's built on PuTTY. It functions like WS_FTP Pro, using a Norton Commander style GUI interface (or Explorer style, if you wish), but is totally secure, since it uses SSH instead of FTP. More on this later...

Anyway, I've been so busy creaming myself that I haven't had a chance to get back to this thread until now. I think you hit the nail on the head. My web site is resolving now, but my eMail is dead. Hopefully, 'they' are fiddling around, trying to, if you'll pardon the pun, resolve the situation.

EDIT

Mail just started working...

EDIT II

This is the dig I'm getting:

$ dig www.lenon.com@ns.nocdirect.con
; <<>> DiG 9.2.1 <<>> www.lenon.com@ns.nocdirect.con
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62626
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;www.lenon.com\@ns.nocdirect.con. IN	A
;; AUTHORITY SECTION:
.			10800	IN	SOA	A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2003042200 1800 900 604800 86400
;; Query time: 53 msec
;; SERVER: 66.227.57.1#53(66.227.57.1)
;; WHEN: Tue Apr 22 13:10:16 2003
;; MSG SIZE  rcvd: 123


$ dig www.lenon.com@ns2.nocdirect.con
; <<>> DiG 9.2.1 <<>> www.lenon.com@ns2.nocdirect.con
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 52143
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;www.lenon.com\@ns2.nocdirect.con. IN	A
;; AUTHORITY SECTION:
.			10800	IN	SOA	A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2003042200 1800 900 604800 86400
;; Query time: 58 msec
;; SERVER: 66.227.57.1#53(66.227.57.1)
;; WHEN: Tue Apr 22 13:10:28 2003
;; MSG SIZE  rcvd: 124



$ dig lenon.com@ns.nocdirect.con
; <<>> DiG 9.2.1 <<>> lenon.com@ns.nocdirect.con
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24368
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;lenon.com\@ns.nocdirect.con.	IN	A
;; AUTHORITY SECTION:
.			10800	IN	SOA	A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2003042200 1800 900 604800 86400
;; Query time: 51 msec
;; SERVER: 66.227.57.1#53(66.227.57.1)
;; WHEN: Tue Apr 22 13:03:47 2003
;; MSG SIZE  rcvd: 119


$ dig lenon.com@ns2.nocdirect.con
; <<>> DiG 9.2.1 <<>> lenon.com@ns2.nocdirect.con
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 35889
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;lenon.com\@ns2.nocdirect.con.	IN	A
;; AUTHORITY SECTION:
.			10800	IN	SOA	A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2003042200 1800 900 604800 86400
;; Query time: 64 msec
;; SERVER: 66.227.57.1#53(66.227.57.1)
;; WHEN: Tue Apr 22 13:04:11 2003
;; MSG SIZE  rcvd: 120