[SOLVED] DuckDNS Shows my VPN Address

NotAComputerGuy · 09-16-2014, 09:24 AM

Hi all,

I've got a VPN and DuckDNS and the "crontab -e" I have setup under instruction through DuckDNS shows the VPN address.

In /etc/network/interfaces I have added the following line:

Code:

up route add 54.186.198.195 gw 192.168.168.1

The IP address is Duck DNS's I believe.

My crontab -e

Code:

 */5 * * * * sh /home/pi/duckdns/duck.sh >/dev/null 2>&1

The script

Code:

echo url="https://www.duckdns.org/update?domains=domainhere&token=tokenhere&ip=" | curl -k -o /home/pi/duckdns/duck.log -K -

Can anyone tell me why it won't go through my router and goes through my VPN?

suicidaleggroll · 09-16-2014, 12:18 PM

I get 54.187.48.241 for the IP of www.duckdns.org.

Do you have any other way of getting your own IP while connected to the VPN? If so I would just set it in the ip= parameter in your script so there's no question about which IP it's going to grab or which interface it's going to go out of.

https://duckdns.org/faqs.jsp

Quote:

Q: can I script my own update?

A: yes you can do this on http or https. you can comma separate the domains if you want to update more than one, the ip parameter is optional, if you leave it blank we detect your gateway ip
https://www.duckdns.org/update?domai...857452b0c1&ip=

NotAComputerGuy · 09-16-2014, 12:23 PM

I'll add that to the interfaces file and see if that fixes things.

Just out of interest, how did you get the IP? I used

Code:

host duckdns.org

Thanks

suicidaleggroll · 09-16-2014, 12:29 PM

host and ping both give me 54.186.198.195 like you have, but if you try to ssh in (doesn't matter if you use port 22, 80, or 443) it switches to 54.187.48.241. I have no good explanation why that is.

Code:

> ssh -vvv -p 443 test@www.duckdns.org
OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013
debug1: Reading configuration data /home/user/.ssh/config
debug1: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to www.duckdns.org [54.186.198.195] port 443.

NotAComputerGuy · 09-17-2014, 05:41 AM

This appears to have fixed it! Thank you so much!