-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

mick crane wrote:
> On 2019-04-11 17:16, mick crane wrote:
>> On 2019-04-11 17:05, Greg Wooledge wrote:
>>> On Thu, Apr 11, 2019 at 05:02:46PM +0100, mick crane wrote:
>>>> I think that is what dynamic ip address services do, change the 
>>>> ipaddress
>>>> but the service has to be on the ISP's router ?
>>>> Do I understand correctly then when your isp/home address changes 
>>>> your box
>>>> broadcasts its domain new address to the internet ?
>>> 
>>> It doesn't have to be on the router.  You can set up a hook in Debian
>>> to run an arbitrary command whenever your IP address is changed by 
>>> DHCP.
>>> This hook receives the old and new IP addresses, and some other 
>>> things,
>>> as environment variables.  It's about 3 lines of code to set it up.  
>>> No
>>> parsing of the output of any ip or ifconfig command is needed.
>>> 
>>> https://mywiki.wooledge.org/IpAddress
>> 
>> I'll have a read but there must be something I don't understand.
>> Thought there was a hierarchy of domain names mapped to ipaddresses
>> that all the different servers can query as to where something is.
>
> Ok I think I see, you can host your own domain if you have a fixed 
> ipaddress but if have ipaddress that changes need to register domain 
> name and have company host it and advertise they know where it is but 
> can change the nameservers for the domain from theirs to yours at 
> changed ipaddress.
> You can't willy nilly broadcast any domain to the internet yourself.

Well, once your domain is registered (for example, mine), you can either


  1. give your registrar the IP address they should point the domain to.
      This is easiest with static IP address assignments from your ISP, 
      but there's no reason you couldn't do it on a dynamic IP

  OR

  2. Use a dynamic DNS provider (e.g. dyndns, no-ip, afraid, many
      others), and have them automatically update the DNS registration
      when your IP address changes.  

Note that for option 2, you tell your registrar to use those other
nameservers, rather than their own.

I use option 2 myself, registered via ... oh I think 1&1 ... but using
no-ip to provide my dyndns (although the IP hasn't changed in well over
a year - I still don't want to be caught unawares :) )


-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEBcqaUD8uEzVNxUrujhHd8xJ5ooEFAlywYO8ACgkQjhHd8xJ5
ooHseAf9EDq3TrI/7tgMnIjaoRbRqXt3UvqpBHMQWY1jbx67SRZm6pe5vYrdMbEC
l56pAdxCGN+m+hbk9+ND+NYhbesm984ySiEciKyKS3Qi06Z0BvZNvEiSQg28BbKU
9c0NFv3a+5lt5WiCsH8W5lZpgY6M3yKlTTOb6b/hZzQYTRUNmr8VpyMh93z8b+je
on7ZmmaGM/6u2ZzlmBzs2liGS4Gf/aBn6sWjxm8w/l+dM5ImMa6RbgOGHZajGfSz
eSFAfKP5gpRDysegflJC4JMS+WFOoZWbnbiomEI8JJAUHCC75YQhZfV43BPiJeiz
PhMSbcbwyUSGB+84emLtbPSrPFBKzw==
=tKhq
-----END PGP SIGNATURE-----

-- 
|_|O|_| 
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

Reply via email to