I am setting up a bind9 dns server, and I have configured the zone file to look like this:

$TTL 2d

$ORIGIN home.example.net.

@   IN  SOA ns.home.example.net.    example.gmail.com. (
    2024081602 ; serial - !!remember to increment each change!!
    12h
    15m
    3w
    2h
)
    IN  NS  ns.home.example.net.

ns  IN  A   10.0.0.35; ip that bind is running on

; -- add dns records bellow

router  IN  A   10.0.0.1

pve1    IN  A   10.0.10.1
pve2    IN  A   10.0.10.2

srv-1   IN  A   10.0.0.35

however when I do a nslookup it also returns two other ipv6:

    Name:   router.home.example.net
    Address: 10.0.0.1
    Name:   router.home.example.net
    Address: 2606:4700:3033::ac43:acb1
    Name:   router.home.example.net
    Address: 2606:4700:3030::6815:1e5a


    Name:   srv-1.home.example.net
    Address: 10.0.0.35
    Name:   srv-1.home.example.net
    Address: 2606:4700:3033::ac43:acb1
    Name:   srv-1.home.example.net
    Address: 2606:4700:3030::6815:1e5a

I cannot ssh into the srv-1 because it uses one of the ipv6 provided, and every A record I add also has both of these ipv6 attached to them. Even if I nslookup from other devices it still returns the same result.

note this is my docker config

version: '3'

services:
  bind9:
    container_name: dns-bind9
    image: ubuntu/bind9:latest
    environment:
      - BIND9_USER=root
    ports:
      - "53:53/tcp"
      - "53:53/udp"
    volumes:
      - ./config:/etc/bind
      - ./cache:/var/cache/bind
      - ./records:/var/lib/bind
    restart: always