My Custom Domain Name Is Not Resolving, What Do I Do?

No ratings


Q: My custom domain name isn't resolving, what do I do?


A: First, make sure you have gone through the custom domain name setup process with the PowerSchool Learning Integrations Team, if you are not sure please read this article.


If you have a custom domain name that isn't resolving, here's something you can try to see if it's pointed to the correct IP address.


If you're on a Mac you can use dig within your Terminal (Macs usually come with dig installed). Dig is basically a command-line tool for querying DNS name servers. You can read more (and download a windows version) here:


You can also try a different command like "ping." However, the ping command relies on your computer's cached DNS routing information, so it's a bit less accurate. If you wanted to try using ping, you could type "ping" into the console and you would get something like this:


$ ping


PING ( 56 data bytes
64 bytes from icmp_seq=0 ttl=56 time=24.972 ms
64 bytes from icmp_seq=1 ttl=56 time=31.198 ms
Request timeout for icmp_seq 2
64 bytes from icmp_seq=3 ttl=56 time=28.417 ms


(The connection will keep pinging until you stop it--you can use ctrl-c to cancel.)


The reason I'm using dig is because I can query the specific server, rather than relying on cached data in my computer.


To start, you can type "dig" and the domain you want to query. The command would look like this:


$ dig


However, at this point, this would still get you a DNS response based on what your local computer is caching.


But! you can make it more specific by adding in the server hosting the domain.


To find the server hosting the domain, you can do a whois lookup within the console by typing the command "whois". A lot of data spits out, but eventually toward the bottom, you will see Name Server listings.


So, using dig, you can include this server information in your command. You'll type "dig @servername". So, in our case, in the command line you would have either


$ dig @ServerName.SampleHost.COM


Since you are pinging the server itself, this is as close as we can get to an authoritative source on what IP the A record is pointing to.

Labels (1)