On 01/11/19 16:07, Scott wrote:
> On Thu, 31 Oct 2019 21:50:57 +0100, Juancho <ete...@notreally.com
> If it's any comfort, you do not suffer alone. (...)
> Without getting into useful details, suffice to say that the lack of
> static IP has proven to not be a problem. There are (free!) DDNS
> services out there that give you all you need to find your way home.
> The NAT issue...I got nothin'. My new carrier didn't impose that on
> me. Maybe one can buy a public IP in that case?
Well, I'm all set on fiber now. I wasn't easy, as I had suspected.
The DynDNS solution you mention, Scott, does not work for me, as I host
my own DNS and therefore my public IP is to be declared in the glue
record for my personal domain at the DNS Registry.
But I had some hiccups in the journey from copper-based ADSL to optical
fiber... After leading the optical cable all the way up to the condo's
fifth floor where my apartment is, they guy doing the physical
installation had some trouble doing the fusing of the optical cable at
the termination point inside the house. He managed to make it work at
the third try, we checked the Internet was reachable and he left. Then,
that same evening, the Internet went down and the PON light went red in
the ONT box. Turns out the fusing was brittle, and it broke. So I had to
phone the installer guy and request a fix, but he is a busy person and
it took him two days to come back and redo the cable fusing.
Which he did. Then I dove into opening the ports I needed open in the
new home router, which proved not to be possible, as I had been assigned
a main IPv6 address and a CGNAT'ed IPv4. I could open ports in the IPv4
address, but through some fucking IPv6-related joke called PCP, which
basically goes like this: you tell it to open port 443/tcp, and it opens
some random port like 20367/tcp in the WAN side and then injects the
traffic into 443/tcp in the LAN side. Not a viable option as public DNS
is hardwired to port 53 and public-facing SMTP is written in stone to
need port 25.
So I contrived some innocent looking lie and headed to my new ISP
support web forums, where I said I have (I really don't) a
domo-controller for the heating and for the air conditioning of the
house, which needs to be reachable at some fixed port from the public
Internet, because that's the way its Chinese manufacturer has born it.
So they acknowledged the problem, and to my amazement promptly removed
my line from their IPv6 pool and landed me with an old trusty, naked
beautiful, pure IPv4 address; with which the router allowed me to open
all the ports I needed to my heart's content.
Then I went to the Registrar through which I bought my personal domain
(which is "Tnaqv.arg", by the way), and sure enough the operation to
change the glue records through their web-based control panel gave a
nasty error when tried. I had to open a support case with them. They
changed themselves the glue record as I told them I needed done; but
they didn't reply to me neither by email (I have an emergency
"Tznvy.pbz" account for these occasions) nor by their support web page.
Which is not all that nice of them.
(So I am now looking to transfer the domain registration with another
Registrar who does not suck. In the past when "Tnaqv.arg" was
French-owned by a team of geeks, it worked well; then it was bought by
some USA-based megacorp, and it has gone downhill ever since in the
customer care department. Any suggestions for a nice, competent,
non-intrusive DNS Registrar whose dealing causes the least friction?)
So, after all that is done, I am now surfing on a symmetric 100 Mbps
fiber-based Internet link (which is the cheapest and slowest I could
buy), and I am no longer paying the Internet service to the incumbent
ISP in my area but to its competitor. (I swear I would have preferred to
remain just as I was before, but I was given no choice as I was fired as
a customer of their copper-based ADSL service.)