It's called a different use of an A record than what I'm used to.
I'm talking about some totally unconnected system on a different network.
Seems kind of odd to me, what's stopping me from calling my own ip address google.com? I don't know what that would do for me, of course.
Like I said, I know that sounds pretty basic but it's a different way of thinking about this for me, i.e. I've realized I could give my home system, which has a static IP, a domain name that is a subdomain of one of our work computers, which would have been really handy like... last year.
Not necessarily a catch though. Many (most?) registrars and web hosts provide name servers free for their users (GoDaddy lets you do this for example). If you can add/edit DNS records can point a subdomain anywhere you like.
You can do that, but nobody believes your nameserver is authoritative for questions about google.com, so it will only affect someone whom you can persuade to use yours as their default nameserver. Everyone else who asks the "com" top-level domain nameservers who is authoritative for google.com is going to be sent to GOOG's nameservers, not yours, so names you define will be invisible to them.
I'm talking about some totally unconnected system on a different network.
Seems kind of odd to me, what's stopping me from calling my own ip address google.com? I don't know what that would do for me, of course.
Like I said, I know that sounds pretty basic but it's a different way of thinking about this for me, i.e. I've realized I could give my home system, which has a static IP, a domain name that is a subdomain of one of our work computers, which would have been really handy like... last year.