Ed McCorduck wrote: > > No, Ben, it makes a lot of sense, thanks so much. Regarding this part > and based on what I said above about how I apparently got WorldSite.ws > to open up access to my Web site just by asking, should I go back to > them and tell them what you said, i.e. "This means that mccordck.ws. > has not been set up to recognize mail seriving or DNS serving," > and ask them to do this, too? I'll wait for your reply to this before > I try any of your other steps. > > The .ws support teams reply is correct. It looks like you transferred your domains SOA to your IP address, but failed to setup a name server to answer your domains DNS requests (see below). Steve Cowles [scowles@voyager scowles]$ dig +trace mccorduck.ws ; <<>> DiG 9.2.1 <<>> +trace mccorduck.ws ;; global options: printcmd . 370304 IN NS B.ROOT-SERVERS.NET. . 370304 IN NS C.ROOT-SERVERS.NET. . 370304 IN NS D.ROOT-SERVERS.NET. . 370304 IN NS E.ROOT-SERVERS.NET. . 370304 IN NS F.ROOT-SERVERS.NET. . 370304 IN NS G.ROOT-SERVERS.NET. . 370304 IN NS H.ROOT-SERVERS.NET. . 370304 IN NS I.ROOT-SERVERS.NET. . 370304 IN NS J.ROOT-SERVERS.NET. . 370304 IN NS K.ROOT-SERVERS.NET. . 370304 IN NS L.ROOT-SERVERS.NET. . 370304 IN NS M.ROOT-SERVERS.NET. . 370304 IN NS A.ROOT-SERVERS.NET. ;; Received 324 bytes from 127.0.0.1#53(127.0.0.1) in 11 ms ws. 172800 IN NS NS2.DNS.ws. ws. 172800 IN NS NS3.DNS.ws. ws. 172800 IN NS NS4.DNS.ws. ws. 172800 IN NS NS5.DNS.ws. ws. 172800 IN NS NS1.DNS.ws. ;; Received 204 bytes from 128.9.0.107#53(B.ROOT-SERVERS.NET) in 64 ms mccorduck.ws. 21600 IN A 24.24.15.155 mccorduck.ws. 21600 IN NS mccorduck.ws. ;; Received 76 bytes from 216.35.187.250#53(NS2.DNS.ws) in 62 ms [scowles@voyager scowles]$ dig @24.24.15.155 mccorduck.ws ns ; <<>> DiG 9.2.1 <<>> @24.24.15.155 mccorduck.ws ns ;; global options: printcmd ;; connection timed out; no servers could be reached [scowles@voyager scowles]$ dig @24.24.15.155 mccorduck.ws soa ; <<>> DiG 9.2.1 <<>> @24.24.15.155 mccorduck.ws soa ;; global options: printcmd ;; connection timed out; no servers could be reached -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
