Dig returns weird info

J

jrozycki

Verified User
Joined
Feb 24, 2005
Messages
5
I have two domains digitalpublishers.com and sprecace.com
both have subdomains email.digitalpublishers.com and email.sprecace.com
both worked fine the other day (they redirect to squirrelmail installation), but now email.sprecace.com doesn't resolve.
here is the dig info: (notice the difference in status

; <<>> DiG 9.2.2-P3 <<>> email.sprecace.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56437
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;email.sprecace.com. IN A

;; AUTHORITY SECTION:
sprecace.com. 6651 IN SOA ns1.digitalpublishers.com. root.sprecace.com. 2006031103 7200 3600 1209600 86400

;; Query time: 1 msec
;; SERVER: 64.59.83.41#53(64.59.83.41)
;; WHEN: Sun Mar 12 10:09:17 2006
;; MSG SIZE rcvd: 99




; <<>> DiG 9.2.2-P3 <<>> email.digitalpublishers.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17681
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 0

;; QUESTION SECTION:
;email.digitalpublishers.com. IN A

;; ANSWER SECTION:
email.digitalpublishers.com. 10229 IN A 64.59.83.71

;; AUTHORITY SECTION:
digitalpublishers.com. 10229 IN NS ns2.digitalpublishers.com.
digitalpublishers.com. 10229 IN NS dans1.digitalpublishers.com.
digitalpublishers.com. 10229 IN NS ns1.digitalpublishers.com.

;; Query time: 1 msec
;; SERVER: 64.59.83.41#53(64.59.83.41)
;; WHEN: Sun Mar 12 10:09:56 2006
;; MSG SIZE rcvd: 117


how do I fix this? As a bandaid, I created a second subdomain so
sq.sprecace.com works and my client can get to his email.
 
First thing to do is create A records for ns1.digitalpublishers.com and for ns2.digitalpublishers.com in the digitalpublishers.com zone.

That's the first error I'm getting in checking so it's impossible to check further.

Jeff
 
my dig record started to look normal prior to your message and me doing anything. ANd my friend says he can get to email.sprecace.com

but I want to fix what you suggest so..in DA I clicked DNS and then digitalpublishers.com
note: There is a da.digitalpublishers.com domain too (this was added by who I get my service with - I am a reseller)
I then added these
ns1.digitalpublishers.com A 64.59.83.71
ns2.digitalpublishers.com A 64.59.83.71

But now I think you wanted me to put the A record under da.digitalpublishers.com zone. ANd if so, then the error messages I keep getting in the control panel make sense

Subject: This is e-mail notification to warn you that your hostname is setup improperly on your system. 02/12/2006
da.digitalpublishers.com, resolves to 127.0.0.1. Please make sure that your hostname resolves to your server ip (64.59.83.71) or else your email may not work correctly.

Solution:

Create an A record for your hostname (da.digitalpublishers.com.) in your DNS control panel. Point the hostname to your server's main IP address. Also check /etc/hosts to ensure that the server ip is correctly set.
====
My email has always worked so I ignored these.

Thanks,
Jeff
 
You're on the right track, but you still have some errors.

ns1.digitalpublishers.com. (remember that trailing dot; it's important) should point to 64.59.83.71 and ns2.digitalpublishers.com. (ditto on the dot :) ) should point to 64.59.83.72.

And they both belong in the DNS zone for digitalpublishers.com.

There should also be an A record for da.digitalpublishers.com. in your digitalpublishers.com zone file, and no separate zone file for da.digitalpublishers.com.

Note that you can use either:

ns1 (without the dot)

or

ns1.digitalpublihsers.com. (with the dot)

as they both mean the same thing.

Jeff
 
Thanks,
It looks like my DNS had nothing to do with the problem.
I have experienced this tracert for the past week.
Is verio screwed up?

$ tracert email.sprecace.com

Tracing route to email.sprecace.com [199.236.4.73]
over a maximum of 30 hops:

1 21 ms 15 ms 10 ms 73.156.44.1
2 12 ms 12 ms 9 ms 68.87.183.193
3 11 ms 9 ms 10 ms 68.87.182.29
4 10 ms 12 ms 11 ms 68.87.182.33
5 39 ms 21 ms 12 ms 68.87.182.46
6 11 ms 11 ms 12 ms 68.87.182.42
7 25 ms 12 ms 11 ms 68.87.182.38
8 12 ms 15 ms 13 ms 68.87.182.213
9 13 ms 13 ms 18 ms 68.87.182.217
10 14 ms 24 ms 12 ms 68.87.182.90
11 19 ms 21 ms 19 ms 12.126.124.69
12 30 ms 27 ms 30 ms tbr2-p010401.n54ny.ip.att.net [12.123.3.5]
13 28 ms 27 ms 28 ms tbr2-cl15.wswdc.ip.att.net [12.122.10.54]
14 27 ms 28 ms 27 ms ggr2-p390.wswdc.ip.att.net [12.123.9.85]
15 72 ms 28 ms 30 ms att-gw.nyc.verio.net [192.205.32.18]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
 
That sure looks like a verio routing problem.

Everything works now (except that tracert isn't a unix command :) ):
Code: 
[jlasman@of1 ~]$  tracert email.sprecace.com
bash: tracert: command not found
[jlasman@of1 ~]$ /usr/sbin/traceroute email.sprecace.com
traceroute to email.sprecace.com (64.59.83.71), 30 hops max, 38 byte packets
 1  * * *
 2  host-216-66-238-158.lcinet.net (216.66.238.158)  9.486 ms  9.284 ms  9.103 ms
 3  f0-0-1-core.lcinet.net (64.30.215.30)  9.987 ms  9.925 ms  10.236 ms
 4  ca-la2-core-oc3.lcinet.net (66.59.246.253)  10.618 ms  11.863 ms  11.368 ms
 5  GigabitEthernet5-0.GW1.LAX1.ALTER.NET (157.130.236.161)  11.585 ms  10.716 ms  10.721 ms
 6  0.so-0-0-0.XL1.LAX1.ALTER.NET (152.63.112.218)  11.846 ms  10.584 ms  11.976 ms
 7  0.so-4-1-0.XL1.LAX9.ALTER.NET (152.63.116.198)  14.969 ms  66.878 ms  14.208 ms
 8  POS6-0.BR3.LAX9.ALTER.NET (152.63.115.1)  14.967 ms  13.943 ms  15.967 ms
 9  204.255.173.18 (204.255.173.18)  13.479 ms  13.584 ms  16.971 ms
10  p16-0-2-3.r21.lsanca03.us.bb.verio.net (129.250.3.158)  14.604 ms  14.191 ms  14.208 ms
11  p64-2-1-0.r21.mlpsca01.us.bb.verio.net (129.250.5.22)  23.472 ms  22.584 ms 23.100 ms
12  p64-1-3-0.r20.snjsca04.us.bb.verio.net (129.250.3.43)  24.081 ms  24.195 ms 23.821 ms
13  p16-1-0-0.r21.chcgil06.us.bb.verio.net (129.250.5.133)  70.451 ms  70.533 ms  70.189 ms
14  xe-9-1.r01.chcgil06.us.bb.verio.net (129.250.4.6)  70.062 ms  71.402 ms  70.185 ms
15  po1.a01.chcgil07.us.ra.verio.net (129.250.25.167)  70.309 ms  71.317 ms  70.796 ms
16  ge-2-2.a01.chcgil07.us.ce.verio.net (128.242.186.170)  76.547 ms  76.413 ms 76.805 ms
17  64.59.83.12 (64.59.83.12)  77.679 ms  76.801 ms  78.290 ms
18  ns1.digitalpublishers.com (64.59.83.71)  77.199 ms  76.374 ms  76.596 ms
[jlasman@of1 ~]$
 
You must log in or register to reply here.
Back
Top