DNS not resolving for *some* people/locations
We created a new sub-domain (via A record) but it is not resolving for everyone. It's been working for me and some others for about a week, but others still cannot access the site. I don't think this is a propagation issue as we created the entry about a week ago. I've been able to ping and resolve the domain from various machines/networks/operating systems/ISP's, but some others cannot.
I've already had the people who cannot resolve the domain name flush their DNS, but with no effect. They can access the site directly via the IP but not the domain name.
This A record is pointing to a different server than the main domain. The registrar is Network Solutions, the host is Media Temple (dv).
Thanks in advance.
Edit: The domain is testing.nicpartnersinc.com. Also, the host is brand spankin' new and this is the first and only domain created on it.
Edit 2:
From location that can resolve domain
$ dig testing.nicpartners.com +trace
; <<>> DiG 9.4.3-P1 <<>> testing.nicpartners.com +trace
;; global options: printcmd
. 355205 IN NS j.root-servers.net.
. 355205 IN NS g.root-servers.net.
. 355205 IN NS m.root-servers.net.
. 355205 IN NS c.root-servers.net.
. 355205 IN NS h.root-servers.net.
. 355205 IN NS i.root-servers.net.
. 355205 IN NS a.root-servers.net.
. 355205 IN NS k.root-servers.net.
. 355205 IN NS d.root-servers.net.
. 355205 IN NS e.root-servers.net.
. 355205 IN NS f.root-servers.net.
. 355205 IN NS l.root-servers.net.
. 355205 IN NS b.root-servers.net.
;; Received 488 bytes from 71.9.127.107#53(71.9.127.107) in 44 ms
com. 172800 IN NS B.GTLD-SERVERS.NET.
com. 172800 IN NS F.GTLD-SERVERS.NET.
com. 172800 IN NS A.GTLD-SERVERS.NET.
com. 172800 IN NS I.GTLD-SERVERS.NET.
com. 172800 IN NS K.GTLD-SERVERS.NET.
com. 172800 IN NS L.GTLD-SERVERS.NET.
com. 172800 IN NS J.GTLD-SERVERS.NET.
com. 172800 IN NS H.GTLD-SERVERS.NET.
com. 172800 IN NS M.GTLD-SERVERS.NET.
com. 172800 IN NS D.GTLD-SERVERS.NET.
com. 172800 IN NS G.GTLD-SERVERS.NET.
com. 172800 IN NS C.GTLD-SERVERS.NET.
com. 172800 IN NS E.GTLD-SERVERS.NET.
;; Received 501 bytes from 192.5.5.241#53(f.root-servers.net) in 45 ms
nicpartners.com. 172800 IN NS ns.compuone.com.
nicpartners.com. 172800 IN NS ns1.compuone.com.
nicpartners.com. 172800 IN NS ns2.compuone.com.
;; Received 151 bytes from 192.12.94.30#53(E.GTLD-SERVERS.NET) in 222 ms
nicpartners.com. 90000 IN SOA ns.compuone.com. admin.compuone.com. 31 900 600 86400 3600
;; Received 110 bytes from 206.71.164.187#53(ns.compuone.com) in 35 ms
In DNS, propagation is based almost entirely on the serial number in the SOA record. If you don't change it, it will break. Some hosting companies let you make changes all over your domain, but then you have to click on a "publish" link of some sort to indicate that you are ready to commit those changes upon the world.
Also, by "subdomain" I assume you mean you are creating a record, not an actual subdomain. That is, you are adding an A record for testing within your domain, not a subdomain. The difference is only really important when you ask questions that DNS types like myself have to answer. A "subdomain" means NS records to delegate to another set of name servers. I am assuming you mean the misused term to mean "an A record."
For the people who can resolve the name, what do they see? The proper A record? If so, then I would think it is a propagation error; try seeing if you can bump up the serial number or add another record (foo?) and see if that also fails to propagate. If it does, well, call your DNS host.
Note that one of the three name servers serving your zone is down: ns1.compuone.com seems to not be up from where I am at least.
I just tested with dig and nicpartnersinc.com has only two name servers (which is not a lot), ns35.worldnic.com and ns36.worldnic.com.
Both reply authoritatively that testing.nicpartnersinc.com does exist, with IPv4 address 70.32.74.40.
So, it should work now.