wannabecraig
asked on
DNS not working for a C-Name record
I have set up DNS records to point to a url of a cloud server.
So I have myurl.mycompany.com pointing to xxx.amazoncloud.com on the c-name section of my DNS zone files. The prolem is on some DNS server this is not seen.
I'm in Ireland and the DNS server I use from my provider can ping the xxx.amazoncloud.com , that's straight to the server, but it can't ping the myurl.mycompany.com
Any ideas?
So I have myurl.mycompany.com pointing to xxx.amazoncloud.com on the c-name section of my DNS zone files. The prolem is on some DNS server this is not seen.
I'm in Ireland and the DNS server I use from my provider can ping the xxx.amazoncloud.com , that's straight to the server, but it can't ping the myurl.mycompany.com
Any ideas?
How are you doing this test? Is possible DNS query is cached and your query has an old value. Try using Nslookup: http://technet.microsoft.com/en-us/library/aa997324(EXCHG.65).aspx
Hello,
I would try re-applying the DNS Settings in your DNS Zone Files for the C-Name. I've had occasions before where they have not applied for whatever reason.
Who is your domain provider?
Also, if you have a server on site then internal DNS made need changing depending on your existing setup.
I would try re-applying the DNS Settings in your DNS Zone Files for the C-Name. I've had occasions before where they have not applied for whatever reason.
Who is your domain provider?
Also, if you have a server on site then internal DNS made need changing depending on your existing setup.
ASKER
nslookup can't find it either.
I called the provider and they can not resolve it their site either.
Out other provider can, (we use the one I'm having a problem with as a backup)
We have our DNZ zone files with Network Solutions.
When we are using the backup it's down't use our internal DNS at all.
I called the provider and they can not resolve it their site either.
Out other provider can, (we use the one I'm having a problem with as a backup)
We have our DNZ zone files with Network Solutions.
When we are using the backup it's down't use our internal DNS at all.
If you would provide the fully qualified domain name, it would be a lot easier to tell you what is or is not working.
When did you create the CNAME? DNS can take up to 48 hours to propagate worldwide.
ASKER
f.live.emusetech.com
Records are up there a few months now.
Records are up there a few months now.
I see the cname record.
f.live.emusetech.com. 7200 IN CNAME verizonlb-234282631.us-eas t-1.elb.am azonaws.co m.
verizonlb-234282631.us-eas t-1.elb.am azonaws.co m. 60 IN A 107.21.247.43
f.live.emusetech.com. 7200 IN CNAME verizonlb-234282631.us-eas
verizonlb-234282631.us-eas
ASKER
HI,
YEah, I can see it too and I can see it on some DNS servers, but not our provider.
YEah, I can see it too and I can see it on some DNS servers, but not our provider.
So, when you do a dig against your provider's DNS servers, you are not seeing that record?
ASKER
I'm on their connection and when I do an nslookup not records are returned.
download dig and use it:
dig f.live.emusetech.com @IP_of_your_provider +trace
and show the results.
dig f.live.emusetech.com @IP_of_your_provider +trace
and show the results.
Check with your provider to see when their DNS servers update.
ASKER
^^
I'm sure they update more than every 3 months no?
I'm sure they update more than every 3 months no?
ASKER
IS this the dig tool you're talking about?
http://members.shaw.ca/nicholas.fong/dig/
http://members.shaw.ca/nicholas.fong/dig/
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Sorry I missed that post.
It will be interesting to see the dig results.
It will be interesting to see the dig results.
ASKER
This is the output:
C:\dig>dig f.live.emusetech.com @159.134.0.1 +trace
; <<>> DiG 9.3.2 <<>> f.live.emusetech.com @159.134.0.1 +trace
; (1 server found)
;; global options: printcmd
. 262593 IN NS l.root-servers.net.
. 400659 IN NS k.root-servers.net.
. 400659 IN NS i.root-servers.net.
. 400659 IN NS g.root-servers.net.
. 400659 IN NS h.root-servers.net.
. 400659 IN NS e.root-servers.net.
. 400659 IN NS b.root-servers.net.
. 400659 IN NS c.root-servers.net.
. 400659 IN NS a.root-servers.net.
. 400659 IN NS d.root-servers.net.
. 400659 IN NS f.root-servers.net.
. 400659 IN NS j.root-servers.net.
. 400659 IN NS m.root-servers.net.
;; Received 228 bytes from 159.134.0.1#53(159.134.0.1 ) in 309 ms
com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
;; Received 498 bytes from 199.7.83.42#53(l.root-serv ers.net) in 85 ms
emusetech.com. 172800 IN NS ns35.worldnic.com.
emusetech.com. 172800 IN NS ns36.worldnic.com.
;; Received 117 bytes from 192.5.6.30#53(a.gtld-serve rs.net) in 176 ms
;; Warning: Message parser reports malformed message packet.
;; Truncated, retrying in TCP mode.
f.live.emusetech.com. 7200 IN CNAME verizonlb-234282631.us-eas t-1.el
b.amazonaws.com.
. 518400 IN NS a.root-servers.net.
. 518400 IN NS b.root-servers.net.
. 518400 IN NS c.root-servers.net.
. 518400 IN NS d.root-servers.net.
. 518400 IN NS e.root-servers.net.
. 518400 IN NS f.root-servers.net.
. 518400 IN NS g.root-servers.net.
. 518400 IN NS h.root-servers.net.
. 518400 IN NS i.root-servers.net.
. 518400 IN NS j.root-servers.net.
. 518400 IN NS k.root-servers.net.
. 518400 IN NS l.root-servers.net.
. 518400 IN NS m.root-servers.net.
;; Received 515 bytes from 205.178.190.18#53(ns35.wor ldnic.com) in 482 ms
C:\dig>dig f.live.emusetech.com @159.134.0.1 +trace
; <<>> DiG 9.3.2 <<>> f.live.emusetech.com @159.134.0.1 +trace
; (1 server found)
;; global options: printcmd
. 262593 IN NS l.root-servers.net.
. 400659 IN NS k.root-servers.net.
. 400659 IN NS i.root-servers.net.
. 400659 IN NS g.root-servers.net.
. 400659 IN NS h.root-servers.net.
. 400659 IN NS e.root-servers.net.
. 400659 IN NS b.root-servers.net.
. 400659 IN NS c.root-servers.net.
. 400659 IN NS a.root-servers.net.
. 400659 IN NS d.root-servers.net.
. 400659 IN NS f.root-servers.net.
. 400659 IN NS j.root-servers.net.
. 400659 IN NS m.root-servers.net.
;; Received 228 bytes from 159.134.0.1#53(159.134.0.1
com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
;; Received 498 bytes from 199.7.83.42#53(l.root-serv
emusetech.com. 172800 IN NS ns35.worldnic.com.
emusetech.com. 172800 IN NS ns36.worldnic.com.
;; Received 117 bytes from 192.5.6.30#53(a.gtld-serve
;; Warning: Message parser reports malformed message packet.
;; Truncated, retrying in TCP mode.
f.live.emusetech.com. 7200 IN CNAME verizonlb-234282631.us-eas
b.amazonaws.com.
. 518400 IN NS a.root-servers.net.
. 518400 IN NS b.root-servers.net.
. 518400 IN NS c.root-servers.net.
. 518400 IN NS d.root-servers.net.
. 518400 IN NS e.root-servers.net.
. 518400 IN NS f.root-servers.net.
. 518400 IN NS g.root-servers.net.
. 518400 IN NS h.root-servers.net.
. 518400 IN NS i.root-servers.net.
. 518400 IN NS j.root-servers.net.
. 518400 IN NS k.root-servers.net.
. 518400 IN NS l.root-servers.net.
. 518400 IN NS m.root-servers.net.
;; Received 515 bytes from 205.178.190.18#53(ns35.wor
Is your provider blocking TCP port 53?
ASKER
Not sure. Some extra info is that if I change my local DNS settings on my PC to google's DNS server it works fine. Not sure if that changes things.
Do you have a split dns zone?
If mycompany.com is also an internal zone then you won't use the external DNS servers for finding any other records. You will need to add the record to the internal zone for name resolution to work.
When you use the External DNS servers from google, you're bypassing the internal DNS servers.
If mycompany.com is also an internal zone then you won't use the external DNS servers for finding any other records. You will need to add the record to the internal zone for name resolution to work.
When you use the External DNS servers from google, you're bypassing the internal DNS servers.
ASKER
Hi, not, there is no split zone. We use this domain name only for our external servers and there is no access to our internal DNS server from this router.